Summary

• Adds deleteCachedResponsesByUrl(urlPrefix) method to Api — removes all cached responses whose request url matches the given prefix, so the next request for any of them fetches fresh data
  • Matching by url (rather than by request params) covers cache keys that cannot be reconstructed at the call site — most commonly keys that embed a serialized request body via extraKey (e.g. data-services snapshot endpoints), which only the original caller can produce
  • Matching stops at path/query boundaries: /users matches /users, /users/1, and /users?page=2, but not /users-archive
• Adds maxAge option to ApiRequestOptions and UseApiQueryOptions — cached entries older than the specified milliseconds are treated as a cache miss, triggering a fresh fetch
• Expired entries are evicted from the cache on read to prevent memory leaks
• Adds parseApiRequestIdUrl helper in lib, co-located with apiRequestId so both directions of the cache-key format live in one module
• Fixes readCachedResponse docs: returns null on cache miss, not undefined

Usage

// Invalidate cached responses after a mutation — evicts the plain list,
// filtered/paginated variants, and POST-based query endpoints whose
// cache keys embed the serialized request body
await api.request(PortfolioGroupEndpoints.update(id, body))
api.deleteCachedResponsesByUrl('/v3/groups/portfolio-groups')
api.deleteCachedResponsesByUrl('/v3/data-services/portfolio-groups')

// Cache with TTL — define as a shared constant per endpoint
export const BROKERS_MAX_AGE = 60_000

api.request(params, { fetchPolicy: 'cache-first', maxAge: BROKERS_MAX_AGE })

useApiQuery(params, { fetchPolicy: 'cache-first', maxAge: BROKERS_MAX_AGE })

Test plan

• deleteCachedResponsesByUrl removes all entries matching the url prefix — next requests go to network
• Matches sub-paths (/users/1) and query variants (/users?page=2) of the prefix
• Does not evict urls that extend the prefix without a path boundary (/users-archive)
• Does not affect entries with non-matching urls
• Is a no-op when no cached entries match
• parseApiRequestIdUrl round-trips the url from apiRequestId
• Cache hit within maxAge — no network request fired
• Cache miss after maxAge expires — network request fires and cache is refreshed
• No maxAge specified — existing cache behaviour unchanged
• Expired entry is removed from cache on read (no memory leak)
• Verified end-to-end in the UI app: admin Portfolio Groups list serves from cache on revisit, and refetches after a portfolio group is created/updated/deleted